-
Notifications
You must be signed in to change notification settings - Fork 5.1k
feat: ContentHero design update #16032
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wackerow looks good, left a question about the hero image dimensions
@@ -73,7 +73,7 @@ export const UpgradeLayout = ({ | |||
const heroProps = { | |||
...frontmatter, | |||
breadcrumbs: { slug, startDepth: 1 }, | |||
heroImg: frontmatter.image, | |||
heroImg: { src: frontmatter.image, width: 5750, height: 4332 }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit unsure about this pattern and whether it's truly needed.
For dynamic images, I assume we'll need to pass width and height for aspect ratio. If so, I'd define these in the ContentHero
component, as all images there will likely require consistent dimensions.
width={760} | ||
height={451} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shouldn't we keep these dimensions to keep the same aspect ratio or a calculated width & height to avoid layout shifts?
Description
Updates ContentHero according to new /what-is-ethereum designs
Preview links
Layer 2 pages
Roadmap layout
Staking layout
Translatathon layout
Upgrade layout
Use cases layout